Skip to content

chore(main): release 0.1.1#4

Merged
lanycrost merged 1 commit intomainfrom
release-please--branches--main--components--github-webhook-impulse
Apr 19, 2026
Merged

chore(main): release 0.1.1#4
lanycrost merged 1 commit intomainfrom
release-please--branches--main--components--github-webhook-impulse

Conversation

@lanycrost
Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.1.1 (2026-04-19)

Miscellaneous

  • harden release automation (b56a32e)
  • update dependencies (2dc4e1f)
  • use dedicated release token for release-please (aaadb50)

This PR was generated with Release Please. See documentation.

@lanycrost lanycrost merged commit 6eb0da7 into main Apr 19, 2026
2 checks passed
@lanycrost
Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

@github-advanced-security
Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants